<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7144/Guardrails-Catalog-How-to-Write-Allowed-Not-Allowed-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7144</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7144&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Guardrails Catalog: How to Write “Allowed / Not Allowed” Requirements </title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7144/Guardrails-Catalog-How-to-Write-Allowed-Not-Allowed-Requirements.aspx</link> 
    <description>This article shows BAs, systems analysts, and product managers how to turn vague AI &amp;ldquo;safety&amp;rdquo; statements into clear, testable requirements. It introduces a simple artifact called a Guardrails Catalog&amp;mdash;a reusable list of Allowed / Not Allowed rules that define boundaries for AI features (forbidden actions, restricted data, safe defaults, and what the system must do instead). The core technique is writing each guardrail like acceptance criteria: specify the trigger, the prohibited outcome, the required safe behavior, the exact refusal wording the user should see, and a straightforward validation step. The article includes practical guardrail patterns and examples (e.g., no irreversible actions without confirmation, redact sensitive identifiers, refuse unauthorized requests, don&amp;rsquo;t guess when ambiguous, don&amp;rsquo;t invent sources) plus a short list of common pitfalls to avoid. A separate downloadable template is linked for teams to copy/paste and use immediately.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 25 Jan 2026 21:25:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7144</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7142/Agentic-AIs-Blind-Spots-A-BAs-Guide-to-GRC-for-Autonomous-Systems.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7142</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7142&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Agentic AI&#39;s Blind Spots: A BA’s Guide to GRC for Autonomous Systems</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7142/Agentic-AIs-Blind-Spots-A-BAs-Guide-to-GRC-for-Autonomous-Systems.aspx</link> 
    <description>The advent of Agentic AI forces a fundamental, non-negotiable re-evaluation of business analysis practice. The GenAI Paradox mandates that the Business Analyst is no longer merely a documenter of known functional requirements , but must evolve into an Architect of Trust: a strategic professional who defines the safe operational boundaries of increasingly autonomous systems.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 19 Jan 2026 23:51:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7142</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7120/AI-Requirements-Starter-Kit.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7120</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7120&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>AI Requirements Starter Kit</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7120/AI-Requirements-Starter-Kit.aspx</link> 
    <description>&amp;ldquo;Let&amp;rsquo;s add AI&amp;rdquo; is not a requirement. It&amp;rsquo;s a vague wish that can turn into a costly prototype, a security headache, or an embarrassing production incident if the basics aren&amp;rsquo;t defined up front.&amp;nbsp;&amp;nbsp;Business Analysts are in the best position to prevent that outcome...
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 15 Dec 2025 00:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7120</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7096/Requirements-Friendly-Data-Dictionary-20.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7096</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7096&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements-Friendly Data Dictionary 2.0</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7096/Requirements-Friendly-Data-Dictionary-20.aspx</link> 
    <description>This article describes using a Requirements-Friendly Data Dictionary (RFDD) as an alternative to representing a software solution&amp;rsquo;s data-related requirements as User Stories, Use Cases, or traditional Waterfall Requirement statements. Any of these forms can still be used to document the solution&amp;rsquo;s functional requirements. An RFDD spreadsheet-based template or extended requirements management tool (RMT) provides a structured format that supports a business analyst documenting required Record and Field details while eliciting functional requirements.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 30 Nov 2025 20:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7096</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7107/Writing-Non-Functional-Requirements-That-Developers-Actually-Use.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7107</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7107&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Writing Non-Functional Requirements That Developers Actually Use</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7107/Writing-Non-Functional-Requirements-That-Developers-Actually-Use.aspx</link> 
    <description>Learn a simple, practical method for turning vague wishes like &amp;ldquo;the system must be fast and secure&amp;rdquo; into concrete, testable non-functional requirements that developers, testers, and ops actually use. This article walks through step-by-step techniques, real-world examples (performance, security, usability, operability), and a quick checklist you can apply to your current projects.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 17 Nov 2025 04:23:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7107</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7054/Prioritizing-Software-Quality-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7054</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7054&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Prioritizing Software Quality Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7054/Prioritizing-Software-Quality-Requirements.aspx</link> 
    <description>You have to determine which quality requirements are most important to your project&amp;rsquo;s success, and then state specific objectives for them so designers can make appropriate choices. This article describes an approach for identifying and specifying the most important quality attributes for your project, adapted from consultant Jim Brosseau&amp;rsquo;s method.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 13 Oct 2025 16:43:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7054</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7009/Keep-Your-Eyes-on-the-Interfaces.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7009</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7009&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Keep Your Eyes on the Interfaces</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7009/Keep-Your-Eyes-on-the-Interfaces.aspx</link> 
    <description>Business analysts must identify external interfaces and the constraints they impose on architecture and detailed designs. Conscientious designers will ensure that all the pieces of a complex system fit together correctly across their mutual interfaces. New components that developers integrate into an existing system must also conform to established interface conventions.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 25 Aug 2025 00:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7009</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6745/Too-Many-Requirements.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6745</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6745&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Too Many Requirements?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6745/Too-Many-Requirements.aspx</link> 
    <description>A reader wrote to me with questions regarding a development project that he thought involved too many requirements and too little flexibility around requirement priorities. (You&amp;rsquo;ve never heard of such a thing before, right?)&amp;nbsp;
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Tue, 13 May 2025 01:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6745</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6718/Translating-EU-MDR-into-Actionable-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6718</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6718&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Translating EU MDR into Actionable Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6718/Translating-EU-MDR-into-Actionable-Requirements.aspx</link> 
    <description>Being a Business Analyst on a healthcare project requires more than just expertise in requirement management; it demands a deep understanding of the regulatory landscape in the target market for medical device release. Compliance with industry standards, such as FDA regulations in the U.S. or MDR in Europe, is critical to ensuring the device meets safety, quality, and legal requirements. A Business Analyst must bridge the gap between technical teams, stakeholders, and regulatory bodies, ensuring that every requirement aligns with market-specific guidelines. This dual responsibility makes their role essential in navigating the complexities of healthcare projects and driving successful product launches.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 06 Apr 2025 20:25:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6718</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6609/Crafting-Valuable-Requirements-Using-Business-Architecture-and-Artificial-Intelligence.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6609</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6609&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Crafting Valuable Requirements Using Business Architecture and Artificial Intelligence</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6609/Crafting-Valuable-Requirements-Using-Business-Architecture-and-Artificial-Intelligence.aspx</link> 
    <description>Planning, managing, and delivering business requirements are daunting undertakings in any organization. It requires a lot of human resources and despite great efforts, the success rate of digital transformation project delivery is usually very low in most organizations, according to Boston Consulting Group and the Harvard Business Review. In this article, we&amp;rsquo;ll touch base on two methodologies that address today&amp;rsquo;s challenges of managing and crafting valuable business requirements, one of which is based on generative artificial intelligence.

Requirement Management in TOGAF Enterprise Architecture

Requirement Management is at the center of enterprise architecture as shown in Figure 1 below. In The Open Group Architecture Framework (TOGAF), a requirement is defined as a statement of need that must be met by the architecture. It typically represents a high-level capability that must be met by the system or enterprise architecture to satisfy a contract, standard, specification, or other formally imposed document. Requirements in TOGAF serve as the basis for planning, defining, designing, and realizing architectural solutions at the business, application, data, and technology levels. They play a crucial role in guiding the development of the architecture to be delivered, ensuring that the final outcome aligns with the strategic goals, stakeholder needs, and operational demands of the organization.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 06 Oct 2024 05:03:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6609</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6602/Requirements-vs-User-Stories-Which-Are-Better.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6602</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6602&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements vs. User Stories: Which Are Better?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6602/Requirements-vs-User-Stories-Which-Are-Better.aspx</link> 
    <description>As someone who has worked as a business analyst for more years than I care to admit, one of the most common questions I get is: &amp;ldquo;Which is better, requirements or user stories?&amp;rdquo; If only the answer were that simple! The truth is, there isn&amp;rsquo;t a clear winner, because they serve different purposes and complement each other in ways that are essential to a successful project.

I&amp;rsquo;ve seen teams try to use only one of the two and miss critical aspects of a project. And I&amp;rsquo;ve seen projects where both were used in tandem, leading to smooth communication, aligned expectations, and a final product that delighted both users and stakeholders. Let me walk you through why both requirements and user stories are important tools in our arsenal as business analysts&amp;mdash;and why, as practitioners, we should never limit ourselves to just one.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 16 Sep 2024 00:29:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6602</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6534/What-Requirements-Are-Needed-When-Implementing-a-COTS-Information-System.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6534</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6534&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What Requirements Are Needed When Implementing a COTS Information System?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6534/What-Requirements-Are-Needed-When-Implementing-a-COTS-Information-System.aspx</link> 
    <description>This article discusses capability-based detailed requirements (DTRs) for a selected Commercial-Off-the-Shelf (COTS) information system. A complete set of DTRs identifies which &amp;ldquo;Out-of-the-Box&amp;rdquo; (OOTB) capabilities are to be implemented as is, which need changing, which aren&amp;rsquo;t needed, and which unsupported capabilities need to be added. A spreadsheet-based template is offered for documenting and managing these requirements.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 07 Jul 2024 19:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6534</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6516/What-Requirements-Are-Needed-When-Selecting-a-COTS-Information-System.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6516</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6516&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What Requirements Are Needed When Selecting a COTS Information System?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6516/What-Requirements-Are-Needed-When-Selecting-a-COTS-Information-System.aspx</link> 
    <description>This article discusses the role of Capability-Based High-Level Requirements (HLRs) when an organization has chosen to acquire a Commercial-Off-The-Shelf (COTS) information system. The objective of the system is to contribute to the solution to a business problem or help take advantage of a business opportunity.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 09 Jun 2024 05:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6516</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6487/Dont-Let-Your-Software-Requirements-Die.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6487</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6487&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Don&#39;t Let Your Software Requirements Die</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6487/Dont-Let-Your-Software-Requirements-Die.aspx</link> 
    <description>In the realm of software development, the clarity and accuracy of software requirements are pivotal for project success. Traditionally viewed as static documents to be archived post-project, this perspective neglects their ongoing potential.

Living software requirements is a paradigm where these documents evolve continually with the software, serving as an enduring source of truth. This approach not only maintains relevance but also actively shapes the software&amp;rsquo;s lifecycle, promoting adaptability and precision in development processes.

They ensure that as software grows and changes, the documentation is not left behind, thus avoiding the pitfalls of outdated or irrelevant information - because often zero documentation is worse than out of date documentation!
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 05 May 2024 22:33:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6487</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6370/The-Psychology-of-Requirements-Elicitation-Unraveling-the-Human-Factors.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6370</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6370&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Psychology of Requirements Elicitation: Unraveling the Human Factors</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6370/The-Psychology-of-Requirements-Elicitation-Unraveling-the-Human-Factors.aspx</link> 
    <description>Requirement elicitation, a critical part of project development, is often perceived as a purely technical process. However, this is not always the case. Effective requirement elicitation relies not only on technical acumen but also on an understanding of how human cognition, biases, and behaviors shape the process and what we can do to mitigate the negative influence of these inherent human factors. In this article, we selected three critical human factors: confirmation bias, the availability heuristic, and groupthink. These factors are commonly experienced in requirement elicitation activities. The article delves into the intricacies of these human aspects of requirement gathering and illustrates their impact using examples. We dissect the impact of these biases on requirement gathering, shedding light on the potential consequences that can arise when they go unchecked. Furthermore, we discuss strategies and techniques for mitigating these biases, emphasizing the role of requirements analysts as impartial facilitators.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 04 Feb 2024 06:08:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6370</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6368/The-Importance-of-Quality-Requirements-in-Software-Development.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6368</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6368&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Importance of Quality Requirements in Software Development</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6368/The-Importance-of-Quality-Requirements-in-Software-Development.aspx</link> 
    <description>Achieving an equilibrium between the desire to produce more functionality and quality requirements is a challenge in most software development projects. Functional requirements are often in the spotlight because of their tangible impact on user experience and business value. But quality requirements silently underpin a system&amp;rsquo;s reliability, security, and robustness. In this article, we delve into the critical role played by quality requirements and the tension most software projects experience in managing these two types of requirements. Navigating the tension between functionality and quality is a challenge. The allure of visible functionality often overshadows quality attributes, leading to the unintentional neglect of quality requirements. This imbalance can result in costly consequences, including operational disruptions, post-release fixes, and damage to an organization&amp;rsquo;s reputation that may be caused by a security breach or a custom data privacy leak. To address this challenge, organizations must empower their technical teams to influence project priorities and actively participate in shaping product quality.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 01 Jan 2024 05:39:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6368</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6385/Fundamentals-of-Non-Functional-Quality-Requirements-in-1-Easy-Lesson.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6385</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6385&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Fundamentals of Non-Functional (Quality) Requirements in 1 Easy Lesson</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6385/Fundamentals-of-Non-Functional-Quality-Requirements-in-1-Easy-Lesson.aspx</link> 
    <description>The objective of this article is to help business analysts deal with the task of eliciting and documenting non-functional requirements (NFRs) - also known as Quality Requirements. It describes NFR fundamentals in terms of who, what, when, where, and why. It&amp;rsquo;s considered one easy lesson because my series on functional requirements needed nine articles, and my series on data fundamentals needed 10.&amp;nbsp;&amp;nbsp;This article assumes that the NFRs are wanted in relation to a software-based solution to a business problem or opportunity. Also assumed is that there are or will be functional requirements for the solution.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 10 Dec 2023 08:35:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6385</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6369/Requirements-in-DevOps-Challenges-and-Exploring-Avenues-for-Integration.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6369</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6369&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements in DevOps: Challenges and Exploring Avenues for Integration</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6369/Requirements-in-DevOps-Challenges-and-Exploring-Avenues-for-Integration.aspx</link> 
    <description>DevOps emphasizes rapid development, continuous integration, and automation, which presents a unique challenge in terms of aligning it with the often more structured and linear process of requirements gathering and documentation. This article discuss this tension between two paradigms and how to harmonize them. In this article, we explore the challenges of harmonizing traditional requirements engineering practices with the dynamic nature of DevOps. By embracing open collaboration, continuous feedback, adaptability, and traceability, DevOps teams can navigate these challenges and pave the way for seamless integration. In the context of DevOps, requirements cannot be static artifacts; they become living entities that evolve in tandem with the software. This article is a reflection on the challenges of integrating RE in DevOps and an exploration of avenues to achieve seamless integration.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 29 Oct 2023 20:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6369</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6362/Elevating-Collaboration-Requirements-Management-Processes-A-Convergence-of-AI-and-Tools.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6362</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6362&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Elevating Collaboration &amp; Requirements Management Processes: A Convergence of AI and Tools</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6362/Elevating-Collaboration-Requirements-Management-Processes-A-Convergence-of-AI-and-Tools.aspx</link> 
    <description>The integration of AI into requirements management signals a transformative juncture, promising heightened efficiency, insightful perspectives, and streamlined processes. While challenges persist, a methodical approach to AI implementation offers a pathway to reaping these benefits. Organizations poised to embrace AI stand to elevate their requirements management processes, fostering superior project outcomes and innovation-driven success.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 24 Sep 2023 19:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6362</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6268/Natural-Language-Processing-for-Requirements-Engineering.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6268</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6268&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Natural Language Processing for Requirements Engineering</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6268/Natural-Language-Processing-for-Requirements-Engineering.aspx</link> 
    <description>Natural Language Processing (NLP) is a branch of artificial intelligence that aims to allow machines to comprehend, interpret, and generate human language. It comprises developing algorithms and models capable of processing natural language input such as text, voice, and pictures in order to do activities traditionally performed by humans. Recent developments in machine learning technology, as well as the availability of large natural language datasets, have allowed NLP to make great strides in recent years. Quality checks, extraction, classification of requirements, requirements modeling, traceability of requirements, and retrieval are the six main areas of focus for NLP tools and studies. In this article, I discuss these advances in NLP for requirements engineering (RE). NLP for requirements engineering is a growing field of study, yet there is a disconnect between research findings and practice. This is because there aren&amp;rsquo;t enough high-quality data sources and domain-specific requirements sources. Despite this, scientific progress has been made in showing potential. The community of practitioners should collaborate with academics and tool suppliers to influence the direction of NPL for RE.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 27 Aug 2023 04:59:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6268</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6288/AI-in-Business-Analysis-Engaging-Stakeholders-with-ChatGPT.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6288</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6288&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>AI in Business Analysis:  Engaging Stakeholders with ChatGPT</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6288/AI-in-Business-Analysis-Engaging-Stakeholders-with-ChatGPT.aspx</link> 
    <description>What role can generative artificial intelligence, such as ChatGPT, play in business analysis? Could it interview a stakeholder? How would it deal with a difficult stakeholder? It depends on how well it&amp;rsquo;s trained.

I set up a scenario with ChatGPT to conduct an interview with a challenging stakeholder. I prepared it with a prompt to prepare for a difficult stakeholder but did not give it any specific objections. A breakdown of the entire prompt follows the interview scenario and transcript below.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 25 Jun 2023 09:57:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6288</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6257/Proven-Strategies-For-Writing-Better-Business-Analysis-Memos.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6257</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6257&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Proven Strategies For Writing Better Business Analysis Memos</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6257/Proven-Strategies-For-Writing-Better-Business-Analysis-Memos.aspx</link> 
    <description>In the fast-paced world of business, communication is key. Business analysts are responsible for providing insights that help drive better decision-making, and effective communication is crucial in delivering those insights. One of the most important communication tools that business analysts use is the business analysis memo. In this article, we&amp;#39;ll explore proven strategies for writing better business analysis memos that will help you communicate your ideas more effectively, drive better business outcomes, and advance your career.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 17 Apr 2023 02:27:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6257</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6203/6-More-Important-Requirements-Practices.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6203</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6203&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>6 More Important Requirements Practices</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6203/6-More-Important-Requirements-Practices.aspx</link> 
    <description>&amp;nbsp;Here are six more practices that, again, virtually every project will find valuable. These are adapted from our book, Software Requirements Essentials: Core Practices for Successful Business Analysis.

Do you have to do them? Of course not&amp;mdash;that&amp;rsquo;s your choice. The requirements police won&amp;rsquo;t hunt you down if you don&amp;rsquo;t. But if you know of any projects that won&amp;rsquo;t find at least five of them valuable, please let us know. We&amp;rsquo;ll notify the Guinness World Records people.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 26 Mar 2023 21:11:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6203</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6111/How-to-remember-50-BABOK-Techniques.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6111</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6111&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to remember 50 BABOK Techniques</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6111/How-to-remember-50-BABOK-Techniques.aspx</link> 
    <description>BABoK v3 techniques are a lot. There are not just 10, 20, or 30 techniques but 50 techniques, to be precise and that&amp;#39;s not a small number!

The human mind can remember 5 to 7 elements at a time and anything more than that is hard to remember.

Then, how can one remember 50 techniques?

&amp;quot;Is it really possible to have a BABoK Techniques Mindmap?&amp;quot;

Many of you may wonder.

So, here&amp;#39;s the Ultimate BABoK techniques mindmap which could save you 40 hours of your International Institute of Business Analysis (IIBA) exam preparation!
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 19 Mar 2023 22:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6111</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6192/Specifying-Requirements-for-Outsourced-Projects.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6192</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6192&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Specifying Requirements for Outsourced Projects</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6192/Specifying-Requirements-for-Outsourced-Projects.aspx</link> 
    <description>Rather than building systems in house, many organizations outsource development to contract development companies. They might outsource the work to take advantage of skills they do not have available in-house, to augment their internal staff, or in an attempt to save money or time. The outsourced development supplier could be located physically nearby, on the other side of the world, or anywhere in between.&amp;nbsp;&amp;nbsp;The role of a business analyst is even more important on these projects than on a co-located project. If the team members are all in one location, developers can walk down the hall to ask the BA a question or to demonstrate newly developed functionality. This close collaboration can&amp;rsquo;t happen in the same way with outsourced development. Compared to in-house development, outsourced&amp;mdash;and particularly offshore&amp;mdash;projects face requirements-related challenges...
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 09 Jan 2023 03:45:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6192</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6150/Evaluating-Candidate-COTS-Packages.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6150</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6150&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Evaluating Candidate COTS Packages</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6150/Evaluating-Candidate-COTS-Packages.aspx</link> 
    <description>Whether you&amp;rsquo;re purchasing a package (also called commercial off-the-shelf, or COTS, products) as part or all of the solution for a new project or implementing a solution in the cloud, you still need requirements. Requirements let you evaluate solution candidates so that you can select the most appropriate package, and then they let you adapt the package to meet your needs.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 23 Oct 2022 23:58:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6150</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6074/The-6-Most-Important-Requirements-Practices.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6074</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6074&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The 6 Most Important Requirements Practices</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6074/The-6-Most-Important-Requirements-Practices.aspx</link> 
    <description>There are many other valuable requirements activities besides these six. However, these practices greatly increase your chances of building a solution that achieves the desired business outcomes efficiently and effectively. Applying them doesn&amp;rsquo;t guarantee success for any BA, product owner, or product manager. But neglecting them likely ensures failure.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 12 Jun 2022 16:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6074</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6061/Using-Feature-Trees-to-Depict-Scope.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6061</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6061&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Using Feature Trees to Depict Scope</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6061/Using-Feature-Trees-to-Depict-Scope.aspx</link> 
    <description>A software feature consists of one or more logically related system capabilities that provide value to a user and are described by a set of functional requirements. Many business analysts use features as a way to describe the scope of a project. However, a simple list doesn&amp;rsquo;t readily show the size and complexity of various features. Nor does quickly skimming a feature list easily reveal the full scope of a project. A feature tree is a visual analysis model that organizes a set of features in a format that makes them easy to understand.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 09 May 2022 03:25:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6061</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6041/Beyond-Good-Requirements-The-Zoom-In-Zoom-Out-Loop.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6041</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6041&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>“Beyond Good Requirements- The Zoom In – Zoom Out Loop”</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6041/Beyond-Good-Requirements-The-Zoom-In-Zoom-Out-Loop.aspx</link> 
    <description>As an analyst you have to ensure your own understanding of the bigger picture. You have to zoom in and zoom out frequently.&amp;nbsp;You need to analyze either in small initiatives the context under which the ba work will take place. It is possible to get so focused on the solution that your thoughts are stuck only in delivering the solution and forgetting to revisit frequently the alignment with the scope and the context.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 17 Apr 2022 16:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6041</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5966/How-to-Create-a-Less-is-More-Stakeholder-Friendly-Data-Model-in-Minutes.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5966</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5966&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to Create a ‘Less is More’ Stakeholder-Friendly Data Model in Minutes</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5966/How-to-Create-a-Less-is-More-Stakeholder-Friendly-Data-Model-in-Minutes.aspx</link> 
    <description>Many BAs struggle to produce &amp;lsquo;normalized&amp;rsquo;, function-independent data models (or don&amp;rsquo;t produce them at all). Very few business stakeholders can appreciate such models as &amp;ldquo;&amp;hellip; a picture worth a thousand words.&amp;rdquo; This article describes an easy-to-create, simple-to-understand view data model. The view is of just those records involved in an information system capability supporting a specific business activity.

NOTE: This article uses the business-friendly terms record and field rather than the usual data modeling terms entity (or class) and attribute.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 09 Jan 2022 05:27:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5966</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5763/Perfect-Your-Requirements-and-Designs-With-Prototypes.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5763</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5763&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Perfect Your Requirements and Designs With Prototypes</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5763/Perfect-Your-Requirements-and-Designs-With-Prototypes.aspx</link> 
    <description>&amp;nbsp; &amp;nbsp; &amp;nbsp;Designing a new product is a messy process. It involves initial brainstorming, rough concepts, false starts, and extensive refinement. Good designs begin with an identified need or opportunity, and they&amp;rsquo;re based on a solid understanding of the product&amp;rsquo;s requirements. No matter how skilled the requirements analyst is or how informed and cooperative the customer participants are, the first set of requirements they develop will be only approximately correct. It takes a process of iterative refinement and validation to accurately understand the requirements for any nontrivial product.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 02 Aug 2021 06:10:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5763</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5873/Product-Requirements--Three-Fundamental-Scenarios.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5873</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5873&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Product Requirements - Three Fundamental Scenarios</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5873/Product-Requirements--Three-Fundamental-Scenarios.aspx</link> 
    <description>Product configuration requirements are a specialized type of requirement when an information system supports product-related needs through data values. Where there are specific changes to business processes needed to sell and/or operate a new product, the requirements for the information system to support activities within those processes involve standard functional requirements.

Whether an information system can support a product though configuration or requires custom development, when an information system is involved there are standard pre-go-live activities that need to be performed (e.g. testing). Requirements support those activities.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 11 Jul 2021 05:23:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5873</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5834/Integration-Requirement-Analysis-Framework.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5834</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5834&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Integration Requirement Analysis Framework</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5834/Integration-Requirement-Analysis-Framework.aspx</link> 
    <description>Integration requirements are critical for any Project&amp;rsquo;s success when Business Processes flow across multiple systems. As a Business Analyst it&amp;rsquo;s our responsibility to understand the end-to-end Business and Systems Process flow and document the hand off as part of the requirements gatherings process. A systematic approach to gather the requirements for integration between systems will ensure that there is a smooth interaction between the systems and hence the Business Process flow. The below Framework on Integration Requirements Analysis provides a systematic approach to document requirements for an Integration Project
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 17 May 2021 00:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5834</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5816/The-Business-Analyst-Role-in-Business-Continuity-Planning.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5816</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5816&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Business Analyst Role in Business Continuity Planning</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5816/The-Business-Analyst-Role-in-Business-Continuity-Planning.aspx</link> 
    <description>&amp;nbsp; &amp;nbsp; &amp;nbsp;Continuity planning can occur at many levels including at the project, department, organizational, or enterprise level. At the project level, a business analyst considers what will happen if a project solution fails or underperforms. This is usually documented in the form of transition requirements. At the higher levels, a business analyst collaborates with organizational leaders in key areas to determine the steps that need to be taken in the occurrence of major events that significantly disrupt business operations. With that said, I&amp;rsquo;ll be discussing the role a business analyst can play in developing an effective continuity plan.

&amp;nbsp; &amp;nbsp; &amp;nbsp;First, let&amp;rsquo;s discuss what a business continuity plan is. Essentially, this is a comprehensive plan to make operational changes that will allow an organization to continue business or services through a crisis, disaster, or operational disruption. The process of developing and maintaining this plan is known as business continuity planning. Typically, business continuity consists of the following three key areas...
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 11 Apr 2021 21:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5816</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5769/Tasks-Mapped-To-Artifacts.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5769</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5769&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Tasks Mapped To Artifacts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5769/Tasks-Mapped-To-Artifacts.aspx</link> 
    <description>The intention of this article is to identify and specify the artifacts listed in the BABOK. These artifacts are listed within the Outputs section of the BABOK tasks. Outputs are described by a paragraph of text within each task. In this article I attempted to expand on these descriptions by adding detail to their content.

It is assumed that each activity produces a tangible output[2]&amp;nbsp;which is consistent with the layout of the BABOK. Those outputs are classed as artifacts with attributes. Each artifact&amp;rsquo;s attribute description is taken from the element description of the tasks that output that artifact. The BABOK element descriptions provide guidelines for activity that produces the attribute, without necessarily defining the information contained in the attribute.That information has been derived from the element description.

Artifacts are derived from the BABOK Output sections. Artifact attributes are derived from the BABOK Element sections. A useful addition to the BABOK might be examples or templates of the outputs.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 07 Feb 2021 21:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5769</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3151/The-Business-Value-of-Better-Requirements.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3151</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3151&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Business Value of Better Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3151/The-Business-Value-of-Better-Requirements.aspx</link> 
    <description>&amp;nbsp;Not every manager is convinced that his team needs to do a better job on requirements development and management or that such an investment will pay off. Numerous industry studies, however, indicate that requirements issues are a pervasive cause of project distress. Let&amp;rsquo;s see why investing in better requirements is a smart business decision for any organization.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 18 Jan 2021 13:24:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3151</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5754/An-Object-Oriented-Analysis-Of-The-BABOK.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5754</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5754&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>An Object-Oriented Analysis Of The BABOK</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5754/An-Object-Oriented-Analysis-Of-The-BABOK.aspx</link> 
    <description>Consider the situation where you are the business analyst who is planning project work according to the BABOK guidelines. The project manager wants to plan their time spent on business analysis activities. You produce a report of the BABOK that shows tasks that the project manager is expected to contribute to.

This article describes an analysis I performed of the Business Analysis Body Of Knowledge v3 (BABOK). The result of this analysis is a model contained in the Visual Paradigm modeling tool. This model captures 461 pages of the BABOK, from the Business Analysis Key Concepts chapter through to the end of the Techniques To Tasks Mapping chapter.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 11 Jan 2021 04:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5754</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5624/Requirements-Life-Cycle-Management-with-Azure-DevOps.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5624</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5624&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements Life Cycle Management with Azure DevOps</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5624/Requirements-Life-Cycle-Management-with-Azure-DevOps.aspx</link> 
    <description>Requirements management is a critical function for business analysis. Requirements management is focused on ensuring that the business users and stakeholders have the following information available...&amp;nbsp;&amp;nbsp;But the more important question to have answer to and where the real business value is delivered in requirements life cycle management is answering the following questions:

    Are the requirements impacting critical business processes?
    Which processes have recurring change?
    Are the requirements priorities aligned to key business processes?
    Which process will be impacted by which requirements?
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 05 Jul 2020 04:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5624</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5585/Use-Cases--The-New-School.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5585</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5585&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Use Cases - The New School</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5585/Use-Cases--The-New-School.aspx</link> 
    <description>In the world of software development Use Cases are one of many very powerful techniques often used these days.&amp;nbsp; Use cases describe how a person or a system interacts with the solution being modeled/built to achieve a goal. Basically, it&amp;rsquo;s a step by step explanation of what a user can do and how the solution must respond.
As any other business analysis technique, use cases have their advantages and disadvantages. One of the main disadvantages of use cases is that this technique is not graphical &amp;ndash; a use case diagram is but use case descriptions are not, and use case descriptions really lack of visualization&amp;nbsp;especially if there are multiple alternative flows and exception flows that branch out and then loop back into the main one.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 20 Apr 2020 02:03:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5585</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5580/Detailed-Requirements-for-Fully-Automating-a-Business-Activity.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5580</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5580&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Detailed Requirements for Fully Automating a Business Activity</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5580/Detailed-Requirements-for-Fully-Automating-a-Business-Activity.aspx</link> 
    <description>This final article in the Requirements in Context series discusses detailed requirements for a fully automated business activity. &amp;lsquo;Fully automated&amp;rsquo; means that the business information system (BIS) is expected to perform the activity from start to finish without user involvement. A simple example is the system automatically posting a monthly fee against customer accounts. A more complex example is the system utilizing customer-specific pricing details to determine the amount charged for a purchase made by a customer.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Tue, 14 Apr 2020 00:08:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5580</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5564/NFR-Cannot-be-forgotten-technique-often-forgotten.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5564</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5564&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>NFR – Cannot be forgotten technique often forgotten</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5564/NFR-Cannot-be-forgotten-technique-often-forgotten.aspx</link> 
    <description>&amp;nbsp;
 First of all, any operating system or solution contains two types of requirements: functional and non-functional. The solution works as a clock, which requires each gear within the solution to be properly functioning. Based on the theory of constraints, any process throughput can only be improved when the constraint or bottleneck is resolved.
 Therefore, no matter how fast the train can run and how many passengers it can carry in one trip (the functional requirements), as long as the NFRs are not met, the performance of the solution (subway system) can only be as good as the non-functional requirements.
 Second, if NFRs are not considered during the business analysis process, it is very likely they were not part of the criteria for solution evaluation. Without consideration of NFRs, the proposed solution may not be evaluated accurately. What was thought to be the best solution may not be a suitable solution at all.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 09 Mar 2020 00:03:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5564</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5529/Detailed-Requirements-for-Data-Importing-and-Exporting.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5529</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5529&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Detailed Requirements for Data Importing and Exporting</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5529/Detailed-Requirements-for-Data-Importing-and-Exporting.aspx</link> 
    <description>It&amp;rsquo;s important for business analysts to recognize that there is a significant amount of non-technical (i.e. business) detail associated with a system interface capability. The interface is either importing data that&amp;rsquo;s needed and available in electronic format from another system, or exporting data in electronic format when it&amp;rsquo;s needed by some other system or organization. The data is either needed in real time or can be processed as a batch job.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 09 Feb 2020 21:09:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5529</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5475/How-Will-It-Work-The-Future-How-Viewpoint.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5475</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5475&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How Will It Work? The Future How Viewpoint...</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5475/How-Will-It-Work-The-Future-How-Viewpoint.aspx</link> 
    <description>The intention of these viewpoints is to make it easier to see and understand the real business problem. This article focuses on the fourth viewpoint, the&amp;nbsp;Future-How, which looks at the solution to the business problem. It does this by assessing alternatives, and then choosing the best solution to that real business problem.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 08 Dec 2019 23:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5475</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5483/Detailed-Requirements-for-User-Interfaces-and-Reports.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5483</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5483&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Detailed Requirements for User Interfaces and Reports</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5483/Detailed-Requirements-for-User-Interfaces-and-Reports.aspx</link> 
    <description>For business analysts working in an environment where there is a gap between SMEs and the delivery of an IT-based solution for business needs, requirements are documented to bridge that gap. You are reading this because you are a business analyst responsible for documenting detailed requirements and, in the case of this article, business needs involving one or more user interfaces (UIs) or reports.

The objective of this article is to answer the question, &amp;ldquo;How much detail is necessary?&amp;rdquo; Spoiler alert &amp;ndash; quite a bit. This is to avoid, as much as possible, a BA having to go back to a SME when designers or developers have business-level questions about a UI or report. Or worse &amp;ndash; designers or developers&amp;nbsp;not&amp;nbsp;asking questions. Instead, making assumptions about what the business needs and proceeding to deliver the solution based on those assumptions.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 01 Dec 2019 23:14:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5483</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5464/9-Types-Of-Requirements-Documents-What-They-Mean-And-Who-Writes-Them.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5464</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5464&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>9 Types Of Requirements Documents: What They Mean And Who Writes Them</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5464/9-Types-Of-Requirements-Documents-What-They-Mean-And-Who-Writes-Them.aspx</link> 
    <description>Requirements documents are used to communicate the aims of a project in a clear, concise way to ensure all stakeholders are on the same page.&amp;nbsp; When we talk about a requirements document we are often referring to a Business Requirements Document - or a BRD.&amp;nbsp; But as well as a BRD, there are 9 other types of requirements documents that a business may want to use while pushing a project through its stages of completion. The type of format to be used depends on the result of the project itself, whether it&amp;rsquo;s a product, service or system, and the particular requirements it has.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Tue, 22 Oct 2019 06:28:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5464</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5439/Managing-Data-Specific-Business-Needs-Using-a-Data-Dictionary.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5439</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5439&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Managing Data-Specific Business Needs Using a Data Dictionary</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5439/Managing-Data-Specific-Business-Needs-Using-a-Data-Dictionary.aspx</link> 
    <description>The previous article in this series discussed ensuring that high-level requirements (HLRs), within the context of an IT-based project, were properly high level. The remainder of articles in the series will look at detail requirements and the need for them to be sufficiently detailed. The objective of this article is to demonstrate how a data dictionary (DD) can be used as a tool for capturing the appropriate level of detail representing data-specific business needs.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 29 Sep 2019 19:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5439</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5444/Trips-R-You-Web-based-Flight-Booking-Case-Study.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5444</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5444&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Trips-R-You Web-based Flight Booking Case Study</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5444/Trips-R-You-Web-based-Flight-Booking-Case-Study.aspx</link> 
    <description>The purpose of the Trips-R-You Flight Booking Case Study is to provide an integrated, end-to-end set of requirement examples. In IIBA&amp;reg; BABOK&amp;reg;&amp;nbsp;V3 terminology, end-to-end means from Business Requirements to Stakeholder Requirements to Solution and Transition Requirements. This case study, and associated artefacts, use the more traditional business terms Goals, High-level Requirements (HLRs), and Detail Requirements. Only functional requirements are addressed, and only within the context of a project chartered to deliver an IT-based solution.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 29 Sep 2019 05:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5444</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/Trips-R-You%20Web-based%20Flight%20Booking%20Case%20Study%20v5.1.pdf" length="1857466" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5429/Build-Requirements-Around-Real-Journeys.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5429</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5429&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Build Requirements Around Real Journeys</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5429/Build-Requirements-Around-Real-Journeys.aspx</link> 
    <description>Let us look at it from a different angle now and derive the requirements out of the customer journeys.&amp;nbsp;&amp;nbsp;It is impossible to introduce a change... if the change is big and you try to implement it in one go.&amp;nbsp; This is the reason we tend to break any solution into smaller components. Each solution component should be small and independent enough to be changed individually in a controlled manner. So that eventually we will compose a new experience out of them. Pretty much like using a set of Lego blocks.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 22 Sep 2019 21:50:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5429</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5360/Requirements-Review-Challenges.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5360</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5360&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements Review Challenges</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5360/Requirements-Review-Challenges.aspx</link> 
    <description>If someone said you could only perform a single quality practice on a software project, what would you choose? I&amp;rsquo;d pick peer reviews of requirements, which I believe are the highest-leverage quality practice we have available today.&amp;nbsp;&amp;nbsp;In a peer review, someone other than the author of a work product examines the product for quality problems and improvement opportunities. Reviewing requirements is a powerful technique. Use them to identify ambiguous or unverifiable requirements, find requirements that aren&amp;rsquo;t sufficiently detailed yet, spot conflicts between requirements, and reveal numerous other problems.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 05 Aug 2019 01:42:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5360</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5356/Making-Requirements-Reusable.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5356</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5356&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Making Requirements Reusable</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5356/Making-Requirements-Reusable.aspx</link> 
    <description>Reuse is an eternal grail for those who seek increased software productivity. Reusing requirements can increase productivity, improve quality, and lead to greater consistency between related systems.
Reuse is not free, though. It presents its own risks, both with regard to reusing existing items and to creating items with good reuse potential. It might take more effort to create high-quality reusable requirements than to write requirements you intend to use only on the current project. In this article&amp;nbsp;we describe some approaches an organization could take to maximize the reuse potential of its requirements.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 07 Jul 2019 12:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5356</guid> 
    
</item>

    </channel>
</rss>